NTISthis.com

Evidence Guide: BSBITA401 - Design databases

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

BSBITA401 - Design databases

What evidence can you provide to prove your understanding of each of the following citeria?

Design database

  1. Review organisational and task requirements to confirm scope and functionality of database design, including data redundancy
  2. Develop a logical data model to identify and classify data into types
  3. Select appropriate software according to organisational and task requirements and required scope and functionality of database
  4. Confirm database design with appropriate person
Review organisational and task requirements to confirm scope and functionality of database design, including data redundancy

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop a logical data model to identify and classify data into types

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Select appropriate software according to organisational and task requirements and required scope and functionality of database

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm database design with appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop database

  1. Set field attributes according to data type and link databases by a common field in accordance with software procedures
  2. Identify primary key to uniquely identify data
  3. Identify foreign keys to establish associations between data
  4. Use software functions and formulae to meet organisational and task requirements
  5. Create password and access system according to organisational and task requirements
Set field attributes according to data type and link databases by a common field in accordance with software procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify primary key to uniquely identify data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify foreign keys to establish associations between data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Use software functions and formulae to meet organisational and task requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create password and access system according to organisational and task requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop queries, forms and reports

  1. Develop queries as required by organisational and task requirements
  2. Develop input screens or forms to access required data
  3. Develop reports according to organisational and task requirements
Develop queries as required by organisational and task requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop input screens or forms to access required data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop reports according to organisational and task requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test and finalise database

  1. Populate database with sample dataset for testing
  2. Assess and document effectiveness of data relationships, query forms and reports
  3. Address any errors in database design
  4. Name and store database in accordance with organisational requirements and exit the application without data loss or damage
  5. Confirm database readiness with appropriate person
Populate database with sample dataset for testing

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assess and document effectiveness of data relationships, query forms and reports

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Address any errors in database design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Name and store database in accordance with organisational requirements and exit the application without data loss or damage

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm database readiness with appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Design database

1.1 Review organisational and task requirements to confirm scope and functionality of database design, including data redundancy

1.2 Develop a logical data model to identify and classify data into types

1.3 Select appropriate software according to organisational and task requirements and required scope and functionality of database

1.4 Confirm database design with appropriate person

2. Develop database

2.1 Set field attributes according to data type and link databases by a common field in accordance with software procedures

2.2 Identify primary key to uniquely identify data

2.3 Identify foreign keys to establish associations between data

2.4 Use software functions and formulae to meet organisational and task requirements

2.5 Create password and access system according to organisational and task requirements

3. Develop queries, forms and reports

3.1 Develop queries as required by organisational and task requirements

3.2 Develop input screens or forms to access required data

3.3 Develop reports according to organisational and task requirements

4. Test and finalise database

4.1 Populate database with sample dataset for testing

4.2 Assess and document effectiveness of data relationships, query forms and reports

4.3 Address any errors in database design

4.4 Name and store database in accordance with organisational requirements and exit the application without data loss or damage

4.5 Confirm database readiness with appropriate person

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Design database

1.1 Review organisational and task requirements to confirm scope and functionality of database design, including data redundancy

1.2 Develop a logical data model to identify and classify data into types

1.3 Select appropriate software according to organisational and task requirements and required scope and functionality of database

1.4 Confirm database design with appropriate person

2. Develop database

2.1 Set field attributes according to data type and link databases by a common field in accordance with software procedures

2.2 Identify primary key to uniquely identify data

2.3 Identify foreign keys to establish associations between data

2.4 Use software functions and formulae to meet organisational and task requirements

2.5 Create password and access system according to organisational and task requirements

3. Develop queries, forms and reports

3.1 Develop queries as required by organisational and task requirements

3.2 Develop input screens or forms to access required data

3.3 Develop reports according to organisational and task requirements

4. Test and finalise database

4.1 Populate database with sample dataset for testing

4.2 Assess and document effectiveness of data relationships, query forms and reports

4.3 Address any errors in database design

4.4 Name and store database in accordance with organisational requirements and exit the application without data loss or damage

4.5 Confirm database readiness with appropriate person